Skip to content

fix(client): use a unified rate limiter for all ACR API calls#51

Merged
lyzustc merged 2 commits intoawslabs:mainfrom
lyzustc:main
Apr 10, 2026
Merged

fix(client): use a unified rate limiter for all ACR API calls#51
lyzustc merged 2 commits intoawslabs:mainfrom
lyzustc:main

Conversation

@lyzustc
Copy link
Copy Markdown
Contributor

@lyzustc lyzustc commented Apr 6, 2026

Use a unified rate limiter for all ACR API calls, this avoids throttle errors in ACR session cancellation.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@luyuzhe111
Copy link
Copy Markdown
Contributor

@lyzustc this is a great improvement! does stop session API and invoke agent API share the same rate limit tho?

@lyzustc
Copy link
Copy Markdown
Contributor Author

lyzustc commented Apr 6, 2026

@lyzustc this is a great improvement! does stop session API and invoke agent API share the same rate limit tho?

I actually don't know if ACR internally uses a shared rate limit. This implementation safely prevents many sessions timeout simultaneously -> too many stop session requests cause throttle.

@lyzustc lyzustc merged commit f96ddce into awslabs:main Apr 10, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants